Telecommunication service employing an electronic information repository storing social network user information, developer information, and mobile network operator information

ABSTRACT

A telecommunication system that carries out telecommunication functions between multiple parties as initiated by the user interaction with a social network application, while maintaining privacy of the device identifiers (phone numbers or static IP addresses assigned to devices) of the participating parties.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/989,859, filed on Aug. 10, 2020, which is a continuation of U.S.application Ser. No. 16/291,476, filed on Mar. 4, 2019, now U.S. Pat.No. 10,743,152, which is a continuation of U.S. application Ser. No.15/432,120, filed on Feb. 14, 2017, now U.S. Pat. No. 10,225,706, whichis a continuation of U.S. application Ser. No. 14/829,337, filed on Aug.18, 2015, now U.S. Pat. No. 9,578,480, which is a continuation of U.S.application Ser. No. 14/094,526, filed on Dec. 2, 2013, now U.S. Pat.No. 9,124,588, which is a continuation of U.S. application Ser. No.12/884,804, filed on Sep. 17, 2010, now U.S. Pat. No. 8,599,857, whichclaims benefits from U.S. Provisional Patent Application No. 61/243,562,filed Sep. 18, 2009 and U.S. Provisional Patent Application No.61/358,690, filed Jun. 25, 2010, the contents of which are herebyincorporated by reference in their entireties.

BACKGROUND OF THE INVENTION Field of the Invention

This invention relates broadly to social network applications that areconnected to online social networks. More particularly, this inventionrelates to providing advanced telecommunication services to users ofsuch social network applications.

State of the Art

An online social network service is a web-based service that provides ameans for users to interact over the Internet in order to build socialnetworks and provide social interactions between such users. Onlinesocial networking services allow users to share ideas, activities,events, and interests within their individual networks. Popular onlinesocial network services in North America include Facebook, Bebo,Twitter, MySpace and LinkedIn. Other online social network services arepopular for other geographic regions.

Some of the online social network services provide a framework thatallows independent software developers (as well as developers of theservice itself) to develop software logic (referred to herein as “socialnetwork applications”) that is connected to the given service such thatthe application can access user profile data maintained by the service.The social network applications typically provide a means for users tointeract over the Internet in order to carry out desired functionality.For example, Facebook employs a framework utilized by a large number ofsocial network applications, including games (such as “FarmVille” byZynga, “Texas HoldEm Poker” by Zynga, “Café World” by Zynga, “PetVille”by Zynga, “Mafia Wars” by Zynga, and “Treasure Island” by Zynga), mediacontent sharing (such as “Mobile” by Facebook), dating services (such as“Zoosk” by Zoosk, Inc.) and others. The frameworks provide a mechanismfor authenticating a particular user. The frameworks also provide amechanism that allows individual users to authorize a particular socialnetwork application. Once a user is authenticated and the particularapplication authorized by the user, the application can access profiledata of the user. Typically, a permissions scheme is implemented toprovide a mechanism for granting access to certain types of user profiledata. For example, Facebook employs a permissions scheme with a defaultstate whereby the authorized application can access all of the publicdata in the user's profile, including name, profile picture, gender, andfriend list. Access to certain types of private data is managed byextended permissions. For example, if an application seeks toincorporate a user's photos, the application, you would request the“user_photos” extended permission. A long list of extended permissiontypes are described athttp://developers.facebook.com/docs/authentication/permissions, hereinincorporated by reference in its entirety. During the authorizationprocess, the user is presented with a UI in which the user can authorizeyour application to access that specific part of her profile.

One of the problems that challenge user of online social networks aswell as social network applications is the inherent inability of thecurrent systems to provide for voice communication amongst users unlessthe users' phone numbers are known.

For example, the SkypeMe application has been developed that allows aSkypeMe/Facebook user to add specific Facebook friends to a list ofSkypeMe/Facebook users and provides for voice and chat services to thelist of SkypeMe/Facebook users on the Skype network. The servicesprovided by the SkypeMe application are limited in nature as the voicecalls and chat requires Skype-enabled end-point devices. Moreover, theSkypeMe services associates a Skype user ID (or online identifier) witha particular Facebook user ID. The Skype user ID identifies the Skypeuser and does not correspond to any particular end point device.Instead, the Skype user ID is used in conjunction with Skype softwareexecuting on any Skype-enabled end-point device to dynamically login tothe Skype network to establish a connection between the Skype-enabledend-point device and the Skype network for communication to the Skypeuser. Finally, from the point of view of the SkypeMe/Facebook user, theSkypeMe service is limited to specific friends (i.e., only those in theusers list of SkypeMe/Facebook users).

In another example, social network applications have been developed thatinclude Call Me functionality that interface to the Google Voiceplatform. The Call Me functionality includes a call widget associatedwith a particular user. The call widget is made accessible to otherusers executing respective social network application. The other userscan click the call widget and enter their respective phone number. Thesocial network application communicates a message(POST/voice/call/connect) to the Google Voice platform that specifiesthe phone numbers for the parties of the call. The phone number for thecalling party is the phone number entered by the user via interactionwith the call widget. The phone number for the called party is the phonenumber of the particular user associated with the call widget.Importantly, the Call Me functionality of the social network applicationand the Google Voice platform requires that the parties expose theirphone numbers for use by the social network applications. The core issueis that a user's phone number is private in nature and there are manyinstances where a user would like to maintain the privacy of his or herphone number. Such instances are commonplace in social networkapplications such as games and dating application where users havelittle personal knowledge of the other online users. Moreover, it can becumbersome for the calling party to enter his or her phone number anduser input errors can cause failures in properly setting up the call.

Similar problems exist for SMS messaging between users of online socialnetworks and social network applications associated therewith socialnetwork users.

Thus, there remains a need for means of voice, SMS as well as otherforms of communication amongst users of online social networks andsocial network applications associated therewith where a user canmaintain the privacy of his or her phone number with respect to thesocial network application that is used to trigger the communication allas well as to the other parties of the communication.

SUMMARY OF THE INVENTION

In accord with one embodiment of the invention, a telecommunicationservice is provided that interfaces to social network applications toprovide for mobile-based telecommunication services (e.g., mobile voicecalls, SMS messaging and other forms of communication) amongst users ofonline social networks and social network applications, wherein theparties of the telecommunication services are identified to thetelecommunication service by their respective user name, screen name,email address or other handle. Such handles are widely or publicallydistributed, and thus more commonly used in online social networks and,more importantly, more anonymous to the identity of the individual useras compared to their telephone number.

In accord with an embodiment of the invention, the telecommunicationservice includes an information repository storing in electronic formsocial network user information including first data corresponding to arespective social network user. The first data includes a useridentifier and at least one device identifier for the respective socialnetwork user. In the preferred embodiment, social network users interactwith the service to register an association to a particular deviceidentifier (e.g., mobile phone number) and store the registered deviceidentifier as part of the first data maintained by the informationrepository. The registration process preferably involves verification ofpossession of the device identified by given device identifier by acommunication loop between the telecommunication service and the givendevice.

The service also includes messaging means for receiving an electronicrequest issued in conjunction with user-execution of a given socialnetwork application. The electronic request is used to initiate atelecommunication function (e.g., voice call) involving a plurality ofsocial network users identified by respective user identifiers includedas part of the electronic request. Importantly, the electronic requestomits any device identifiers for the plurality of social network usersidentified by respective user identifiers included as part of theelectronic request. The service further includes database access meansfor retrieving from the information repository at least one deviceidentifier corresponding to a respective user identifier included aspart of the electronic request, and means for initiating thetelecommunication function corresponding to the electronic request. Thetelecommunication function includes communication to at least one devicefor a respective social networking user, wherein the at least one deviceis identified by the corresponding device identifier as retrieved fromthe information repository.

In this manner, the service carries out the requested telecommunicationfunction while maintaining the privacy of the device identifiers (phonenumbers or static IP addresses assigned to devices) with respect to theparties as well as to the social network application that was used toinitiate the function. This affords greater protection against unwanteddistribution of the private phone numbers of the parties.

The information repository can be adapted to maintain useful informationpertinent to both the application developers and the operator(s)servicing the calls initiated by the service as control access to suchinformation so as to maintain privacy of the stored information.

Additional objects and advantages of the invention will become apparentto those skilled in the art upon reference to the detailed descriptiontaken in conjunction with the provided figures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system level block diagram of online social networks andsocial network applications together with a telecommunication systemthat interfaces thereto to provide for advanced telecommunicationfunctions between users in accordance with the present invention.

FIGS. 2A1 through 2A3, collectively, is a flow chart illustratingexemplary operations of the elements of the system of FIG. 1 inservicing advanced telecommunication functions between users of thesocial network applications in accordance with a first embodiment of thepresent invention.

FIGS. 2B1 through 2B3, collectively, is a flow chart illustratingexemplary operations of the elements of the system of FIG. 1 inservicing advanced telecommunication functions between users of thesocial network applications in accordance with a second embodiment ofthe present invention.

FIG. 3 is a schematic illustration of the information stored in the ENUMdatabase of the calling service of FIG. 1 .

FIG. 4A is a schematic illustration of the calling party Call-Setup Loopperformed as part of the operations of FIGS. 2A1-2B3.

FIG. 4B is a schematic illustration of the called party Call-Setup Loopperformed as part of the operations of FIGS. 2A1-2B3.

FIGS. 5A through 5B, collectively, is a flow chart illustratingoperations for interacting with a user of the service to register phonenumber information with the user.

FIG. 6 is a flow chart illustrating operations for issuing anapplication developer a developer key and storing the developer key inthe ENUM database of FIG. 1 ; the stored developer key is used forsubsequent authentication of service request messages communicated fromthe social network application of the developer to the calling service.

FIGS. 7A-7C, collectively, is an exemplary message flow diagramillustrating the operations carried out by the system of FIG. 1 inaccordance with the present invention, the message flow provisionsresources (and tears down such resources) that carry out a voice callbetween a calling party mobile device and a called party mobile deviceas initiated by the user interaction with a social network application.

FIG. 8 is a block diagram of a distribute softswitch architecture thatcan be used as part of the system of FIG. 1 .

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

As used herein, a “key” is information (preferably a sequence ofalphanumeric characters or hex string) of fixed length) that is assignedto an entity to authenticate data related to the entity.

As used herein, a “domain key” is a key that is assigned to a givensocial network service to authenticate data related to the given socialnetwork service.

As used herein, an “application key” is a key that is assigned to agiven social network application to authenticate data related to thegiven social network application.

In accordance with the present invention, a telecommunication service isprovided that includes an information repository storing in electronicform social network user information including first data correspondingto a respective social network user. The first data comprises a useridentifier and at least one device identifier for the respective socialnetwork user. In the preferred embodiment, social network users interactwith the service to register an association to a particular deviceidentifier (e.g., mobile phone number) and store the registered deviceidentifier as part of the first data maintained by the informationrepository. The registration process preferably involves verification ofpossession of the device identified by given device identifier by acommunication loop between the telecommunication service and the givendevice.

The service also includes messaging means for receiving an electronicrequest issued in conjunction with user-execution of a given socialnetwork application. The electronic request is used to initiate atelecommunication function (e.g., voice call) involving a plurality ofsocial network users identified by respective user identifiers includedas part of the electronic request. Importantly, the electronic requestomits any device identifiers for the plurality of social network usersidentified by respective user identifiers included as part of theelectronic request. The service further includes database access meansfor retrieving from the information repository at least one deviceidentifier corresponding to a respective user identifier included aspart of the electronic request, and means for initiating thetelecommunication function corresponding to the electronic request. Thetelecommunication function includes communication to at least one devicefor a respective social networking user, wherein the at least one deviceis identified by the corresponding device identifier as retrieved fromthe information repository.

In this manner, the service carries out the requested telecommunicationfunction while maintaining the privacy of the device identifiers (phonenumbers or static IP addresses assigned to devices) with respect to theparties as well as to the social network application that was used toinitiate the function. By maintaining such privacy, the deviceidentifiers (phone numbers) are hidden from (i.e., not presented to) theparties as well as to the social network application that was used toinitiate the function. This affords greater protection against unwanteddistribution of the private phone numbers of the parties.

The information repository can be adapted to maintain useful informationpertinent to both the application developers and the operator(s)servicing the calls initiated by the service as control access to suchinformation so as to maintain privacy of the stored information.

FIG. 1 illustrates an exemplary embodiment of a telecommunicationservice 21 in accordance with the present invention. The service 21allows social network applications to invoke voice communication amongstusers' mobile devices as part of the respective social networkapplication. The service 21 interfaces to social network applicationlogic (e.g., App Logic 18A) for servicing voice calls betweenapplication users as initiated by user interaction with the respectiveapplication. The calling service 21 can interface to multiple socialnetwork applications (e.g., App Logic 18A and 20A) that are connected tothe same online social network 14A and/or can interface to multiplesocial network applications (e.g., SN App Logic 18A and 18B) that areconnected to different online social networks (e.g., 14A and 14B) asshown. The service 21 is particular adapted to service voice callsthrough one or more mobile network operator (MNO) networks as shown inFIG. 1 , but can readily be adapted to service voice calls through otheroperator networks such as LECs servicing POTS lines and VOIP serviceproviders servicing VOIP telephony lines.

In a first embodiment of the present invention, the social networkapplications (e.g., App Logic 18A, 20A, 18B, 20B) and the service 21cooperate to initiate and service a voice call between users as providedin the flow chart of FIGS. 2A1 through 2A3. The operations begin inblock 201, where a user (user A) operates user device 12A and invokes asocial network application (referred to as “App Logic 1” and labeled18A) via the Internet. In response thereto, the social networkapplication 18A connects to the online social network service I (14A)through framework 16A to authenticate the user A, e.g., a logon processfor the service, for example, using the user name (billyway) andpassword (XXXX) assigned to user A. The framework 16A also provides forauthorization that controls access by the social network application 18Ato user A profile data (if such authorization has not yet beenprovided).

In block 203, once user A is authenticated and the applicationauthorized, the social network application 18A and the framework 16Aprovide a mechanism (for example, a token) that allows the socialnetwork application 18A to access user A profile data via the framework16A.

Similar operations are carried out by another user (userB—tomjones@facebook.com) to invoke and execute the social networkapplication (referred to as “App Logic 1” and labeled 18A) via theInternet.

In block 205, during execution of the social network application 18A,the application 18A presents user A with a link (or widget or otheruser-interface element) that is adapted to initiate a voice call to userB upon user interaction with the element. User A then interacts with theelement (for example, by clicking on the link) to initiate a voice callto user B, and the application 18A is notified of the request (forexample, by an HTTP request). User A is thus designated the callingparty and user B is designated the called party throughout. It iscontemplated that the application-drive initiation of voice calls can bepart of many different application scenarios. For example, during a gameapplication, a user can encounter an avatar for one or more other activeusers. In this scenario, the game application can present a link (orwidget or other user-interface element) that is adapted to initiate avoice call between the active users (i.e., between user A and user B).In other example, during a media sharing application, a user can sharemedia with one or more other active users. In this scenario, the mediasharing application can present a link (or widget or otheruser-interface element) that is adapted to initiate a voice call betweenthe active users (i.e., between user A and user B). In yet anotherexample, during a dating application, a user can view a profile of otherusers of the application. In this scenario, the dating application canpresent a link (or widget or other user-interface element) that isadapted to initiate a voice call between users (i.e., between user A anduser B).

In response to the request initiated in block 205, the application 18Agenerates and sends a message to messaging interface 22 of the service21 over a communication link therebetween (block 207). In the preferredembodiment, the message is carried over an IP packet-based communicationnetwork linking the application 18A and the calling service 21 includingthe Internet as shown. The message preferably conforms to the SOAP/XMLprotocol to allow for efficient exchange of the information within themessage. Alternatively, the message can conform to a predeterminedRESTful architecture. This message includes the following:

-   -   user name (billyway) and social network domain (facebook.com)        for the calling party;    -   user name (tomjones) and social network domain (facebook.com)        for the calling party;    -   a domain key for the corresponding social network domain (e.g.,        DK for facebook.com); and    -   an application key for the requesting social network application        (18A).

In block 209, the messaging interface 22 of the service 21 receives themessage communicated from application 18A in block 207 and controls thelogic block 24 to perform a lookup of the information repository 26 inblock 211.

As shown in FIG. 3 , the information repository 26 stores information inelectronic form, the information pertaining to social network users ofthe service 21, social network application developers and the socialnetwork applications that interface to the service 21, and one or moreMNOs that provide resources for connecting calls to the social networkusers of the service 21. The information repository 26 further storeselectronic information pertaining to the calls carried out by operationof the service 21. Access to information repository 26 is controlledaccording to each of the three user types (type 1—social network usersof the service, type 2—developer users associated with social networkapplication developers that develop and/or maintain social networkapplications that interface to the service, and type 3—MNO users thatare associated with MNOs that provide resources for connecting calls tosocial network users of the service).

For the type 1 social network users, a given social network user canaccess the information stored in the information repository 26 for thegiven social network user (examples of such information is outlined incolumn 26A of FIG. 3 ). Access to the information stored in theinformation repository 26 for the given social network user is blockedfor all other social network users as well as all type 2 developer usersand all type 3 MNO users.

For the type 2 developer users, a given developer user can access theinformation stored in the information repository 26 that pertains toapplications developed and/or maintained by the application developerassociated therewith (examples of such information is outlined in column26B of FIG. 3 ). Access to the information stored in the informationrepository 26 that pertains to such applications is blocked fordeveloper users associated with other application developers, for alltype 1 social network users and for all type 3 MNO users.

For the type 3 MNO users, a given MNO user can access the informationstored in the information repository 26 that pertains to the MNOassociated therewith (examples of such information is outlined in column26C of FIG. 3 ). Access to the information stored in the informationrepository 26 that pertains to the given MNO is blocked for MNO usersassociated with other MNOs, for all type 1 social network users, and forall type 2 developer users.

In the preferred embodiment, the information repository 26 is realizedby an SQL database system. A type 1 user name is defined for each socialnetwork user of the service 21, a type 2 user group and name is definedfor each application developer and associated developer user of theservice 21, and a type 3 user group and name is defined for each MNO andassociated MNO user group of the service 21.

The social network user information (26A) is realized by a set of tablesand views associated with a particular social network user in the SQLdatabase system. Permissions associated with such tables and views aredefined that allow for selection and reading of data from such tablesand views by the particular social network user while disallowing theselection and reading of data from such tables and views by all othertype 1 social network users, by any type 2 developer user and by anytype 3 MNO user.

The developer information (26B) is realized by a set of tables and viewsassociated with application developed and/or maintained by a particularapplication developer in the SQL database system. Permissions associatedwith such tables and views are defined that allow for selection andreading of data from such tables and views by all type 2 developer usersthat belong to the group associated with the particular applicationdeveloper while disallowing the selection and reading of data from suchtables and views by all type 2 developer user that belongs to groupsassociated with other application developers, by any type 1 socialnetwork user and by any type 3 MNO user.

The MNO information (26C) is realized by a set of tables and viewsassociated with a particular MNO in the SQL database system. Permissionsassociated with such tables and views are defined that allow forselection and reading of data from such tables and views by all type 3MNO users that belong to the group associated with the particular MNOwhile disallowing the selection and reading of data from such tables andviews by all type 3 MNO users that belong to groups associated withother MNOs, by any type 1 social network user and by any type 2developer user.

The access logic 43 (which can be realized by an HTTP server orapplication server) provides for controlled access to SQL databasesystem by social network users, developer users and MNO users via dataexchange over the Internet. Access is controlled utilizing unique accesskeys that are assigned to the respective social network users, developerusers and MNO users of the service 21. In the preferred embodiment, theaccess key for a given social network user is a user name and passwordassociated with the given social network user, while the access key foreach given developer user and MNO user is secret key assigned thereto.Alternatively, the access key for a given social network user can betied into the authentication mechanism (e.g., an authentication token)for the social network to which the user belongs. The access logic 43maps a request issued by a particular social network user (as identifiedby the corresponding access key assigned to the particular socialnetwork user) into one or more appropriate SQL statements by theparticular social network user, queries the SQL database with such SQLstatement(s), and returns the pertinent information retrieved from theSQL database system to the requesting social networking user. Similarly,the access logic 43 maps a request issued by a particular developer user(as identified by the corresponding access key assigned to theparticular developer user) into one or more appropriate SQL statementsby the particular developer user, queries the SQL database with such SQLstatement(s), and returns the pertinent information retrieved from theSQL database system to the requesting developer user. Moreover, theaccess logic 43 maps a request issued by a particular MNO user (asidentified by the corresponding access key assigned to the particularMNO user) into one or more appropriate SQL statements by the particularMNO user, queries the SQL database with such SQL statement(s), andreturns the pertinent information retrieved from the SQL database systemto the requesting MNO user. In this manner, access control for the threeparts 26A, 26B, 26C is provided by the permissions defined for the SQLdatabase. In alternate embodiments, separate SQL database systems can beused for each logical partition 26A, 26B, 26C of the informationrepository 26.

In block 211, the query of the information repository 26 retrieves thefollowing:

-   -   mobile device phone number, mobile carrier ID, and possibly        other user information (for example, calling rules) for the        calling party (billyway@facebook.com); and    -   mobile device phone number, mobile carrier ID, and possibly        other user information (for example, calling rules or blacklist        parameters) for the called party (tomjones@facebook.com).

In block 213, logic block 24 determines whether the call should beblocked. For example, the calling rules or blacklist info of the calledparty as retrieved from the information repository 26 can dictate thatthe call should be blocked (or not). In yet another example, the callingrules of the calling party as retrieved from the information repository26 can dictate that the call should be blocked (or not). In the eventthat logic block 24 determines that the call should be blocked, theprocessing continues to block 231. Otherwise, the processing continuesto block 215.

Blocks 215 and 217 involves the control of the softswitch 28 that ispart of the service 21. The softswitch 28 includes switching logic thatis controlled by a calling agent. The switching logic includes resourcesthat provide for bridging of connections that carry the bearer trafficfor the legs of the call. The switching logic of the softswitch 28 canalso include media gateway functionality, such as media conversion fordifferent transmission and coding protocols. The calling agent of thesoftswitch 28 (under control of logic block 24) performs a provisioningloop (block 215 and 217) that initiates call set-up and signaling to thegateway function (e.g., 32A or 32B) of the MNO for each leg of the callin order to set-up a connection that carries the bearer traffic for eachleg of the call. The calling agent can provide for translation of callsetup and signaling messages (e.g., from SIP to H.323 and vice versa orbetween other signaling protocols) and thus bridge calls usingincompatible protocols. The calling agent can also employ an E.164 ENUMquery to translate the E.164 number of the calling party and/or calledparty (as provided by the lookup to information repository 26) to acorresponding SIP address or URL for call setup and signaling purposes,if need be.

In the preferred embodiment, the softswitch 28 operates in a proxy modein which both the call setup and signaling messages as well as thebearer traffic for each leg of the call flow through the softswitch 28.This configuration establishes connections between users while keepingtheir phone numbers private. In this proxy mode, the softswitch 28 canexercise full control over the call and disconnect calls in progress ifnecessary. The call set-up and signaling messages communicated betweenthe calling agent of the softswitch 28 and the call-setup-functions(30A, 30B) of the respective MNO networks are carried out of band andcan be realized by IP signaling (such as SIP, MGCP or Megaco signaling),SS7 signaling, or other suitable signaling mechanisms. The bearertraffic communicated between the softswitch 28 and the MNO networks forthe legs of the call is preferably carried by IP trunks or othersuitable network links (labeled 40A and 40B in FIG. 1 ).

In the exemplary embodiment, in block 215 the calling agent of thesoftswitch 28 cooperates with the call-setup-function (30A or 30B) ofthe MNO network for the calling party (preferably identified by the MNOID of the calling party as retrieved from the information repository 26)to set up a connection (i.e., communication session) that carries bearertraffic for the leg of the call to the mobile device (29A or 29B) of thecalling party. At the MNO side, the call-setup-function (30A or 30B) ofthe respective MNO network interfaces to a Radio Network Controller (RNC34A or 34B) to carry out signaling functions with the calling partymobile device. If the call is accepted on the calling party mobiledevice, the call-setup-function (30A or 30B) of the respective MNOnetwork interfaces to the corresponding gateway function (32A or 32B) toallocate resources to provide bearer traffic to and from the callingparty mobile device (via the Base Station (36A or 36B) and RNC (34A or34B) coupled to the calling party mobile device) over the connection tothe softswitch 28. Typically, the respective gateway function (32A and32B) provides media mapping and/or transcoding functions betweenpotentially dissimilar networks.

In this manner, the resources of the MNO network of the calling partyprovides for bi-directional exchange of bearer traffic between thecalling party mobile device and the softswitch 28. In 3G CDMAarchitectures, the gateway function (32A or 32B) of the MNO network iscarried out by the Media Gateway (MGW), and the gateway control function(30A, 30B) is carried out by the MSC Server. In IMS architectures, thegateway function (32A or 32B) of the MNO network is carried out by theIMS Media Gateway (IMS-MGW), and the gateway control function (30A, 30B)is carried out by call session control functions (e.g., I-CSCF, S-CSCFand P-SCSF) in conjunction with the Media Gateway Control Function(MGCF). IN LTE-SAE architectures, the RNC and gateway functions (34A/32Aor 34B/32B) of the MNO network is carried out by the Gateway (GW), andthe gateway control function (30A, 30B) is carried out by the mobilitymanagement entity (MME). Similar functional elements are used in otherarchitectures.

In block 217, the calling agent of the softswitch 28 cooperates with thecall-setup-function (30A or 30B) of the MNO network for the called party(preferably identified by the MNO ID of the called party as retrievedfrom the information repository database 26) to set up a connection(i.e., communication session) that carries bearer traffic for the leg ofthe call to the mobile device (29A or 29B) of the called party. At theMNO side, the call-setup-function (30A or 30B) of the respective MNOnetwork interfaces to a RNC (34A or 34B) to carry out signalingfunctions with the called party mobile device. If the call is acceptedon the called party mobile device, the call-setup-function (30A or 30B)of the respective MNO network interfaces to the corresponding gatewayfunction (32A or 32B) to allocate resources to provide bearer traffic toand from the called party mobile device (via the Base Station (36A or36B) and RNC (34A or 34B) coupled to the calling party mobile device)over the connection to the softswitch 28. Typically, the respectivegateway function (32A and 32B) provides media mapping and/or transcodingfunctions between potentially dissimilar networks. In this manner, theresources of the MNO network for the called party provides forbi-directional exchange of bearer traffic between the called partymobile device and the softswitch 28.

As shown in detail in FIG. 4A, the calling party provisioning loop ofblock 215 involves the exchange of messages between the calling agent ofthe softswitch 28 and the call-setup-function (30A or 30B) of therespective MNO network for the calling party mobile device.Communication of such messages can be achieved by means of commonprotocols such Session Initiation Protocol (SIP) as shown. Othersignaling protocols such as MGCP or Megaco and SS7 signaling can also beused. These messages include a provisioning request message (e.g., SIPrequest) communicated from the softswitch 28 to the call-setup-function(30A or 30B) that carries the mobile device phone number of the callingparty and possibly call profile data. The call profile data can provideinformation related to the call that can be used for authorizationand/or accounting purposes by the respective MNO. Thecall-setup-function (30A or 30B) of the MNO network utilizes the mobiledevice phone number and the call profile data to selectively authorizethe call. The call profile data can be used for accounting purposes bythe MNO as needed. The call-setup-function (30A or 30B) of the MNOnetwork returns a response (e.g., SIP response) to the calling agent ofthe softswitch 28 that carries an indication of connection authorization(or rejection), connection parameters (when authorized) and possiblyother information, such as rate information for the call.

As shown in detail in FIG. 4B, the called party provisioning loop ofblock 217 involves the exchange of messages between the calling agent ofthe softswitch 28 and the call-setup-function (30A or 30B) of therespective MNO network of the called party mobile device. Communicationof such messages can be achieved by means of common protocols suchSession Initiation Protocol (SIP) as shown. Other signaling protocolssuch as MGCP or Megaco and SS7 signaling can also be used. Thesemessages include a provisioning request message (e.g., SIP request)communicated from the softswitch 28 to the call-setup-function (30A or30B) that carries the mobile device phone number of the called party andpossibly call profile data. The call profile data can provideinformation related to the call that can be used for authorizationand/or accounting purposes by the respective MNO. Thecall-setup-function (30A or 30B) of the MNO utilizes the mobile devicephone number and the call profile data to selectively authorize thecall. The call profile data can be used for accounting purposes by theMNO as needed. The call-setup-function (30A or 30B) of the MNO networkreturns a response (e.g., SIP response) to the calling agent of thesoftswitch 28 that carries an indication of connection authorization (orrejection), connection parameters (when authorized) and possibly otherinformation, such as rate information for the call.

In the exemplary embodiment shown in FIG. 4A, the call profile datacommunicated to the call-setup-function of the MNO network in thecalling party provisioning loop of block 215 includes data identifyingthe social network application that initiated the call request messageto the service (block 207) as well as the geographic location of thecalled party mobile device. In this example, the calling party user hasa rate plan associated with calls initiated from a particular socialnetwork application (or group of social network applications). Forexample, the rate plan can provide for tiers of rates for minutes perbilling period (e.g., $6 for the first 100 minutes and $0.20/minutethereafter for calls initiated from a particular social networkapplication (or group of social network applications). The rate plan canalso be limited to calls to endpoints located in limited geographicalregions (for example, to mobile devices located only in the UnitedStates—National Calling only). In this case, the call-setup-function(30A or 30B) of the MNO network cooperates with the Home SubscriberServer (HSS), or other similar logic of the MNO network, to identify thepertinent calling party rate plan corresponding to the social networkapplication as identified by the data supplied thereto, and utilizes thegeographic location of the called party mobile device to authorize thecall in the event that the called party mobile device is within thelimited geographical area of the calling party rate plan (or reject thecall in the event that the called party mobile device is outside thelimited geographical area of the calling party rate plan). Moreover, thepertinent calling party rate plan corresponding to the request is usedfor accounting purposes for billing the call. In alternative embodiment,the call profile data communicated to the call-setup-function of the MNOnetwork in the calling party provisioning loop of block 215 can includethe mobile phone number of the called party mobile device for use inauthorizing the call and billing. The MNO network can be adapted to hidethe mobile phone number of called party mobile device as part of theinformation communicated to the calling party mobile device during callsetup as well as on the billing statements of the calling party. Thecall-setup-function (30A or 30B) of the MNO network returns a response(e.g., SIP response) to the service softswitch 28 that carries anindication of connection authorization (or rejection), connectionparameters (when authorized) and possibly other information, such asrate information for the call.

Similarly, in the exemplary embodiment shown in FIG. 4B, the callprofile data communicated to the call-setup-function of the MNO networkin the called party provisioning loop of block 217 includes dataidentifying the social network application that initiated the callrequest message to the service (block 207) as well as the geographiclocation of the calling party mobile device. In this example, the calledparty user has a rate plan associated with calls initiated from aparticular social network application (or group of social networkapplications). For example, the rate plan can provide for tiers of ratesfor minutes per billing period for calls initiated from a particularsocial network application (or group of social network applications).The rate plan can also be limited to calls to endpoints located inlimited geographical regions. In this case, the call-setup-function (30Aor 30B) of the MNO network cooperates with the HSS (or other similarlogic) of the MNO network to identify the pertinent called party rateplan corresponding to the social network application as identified bythe data supplied thereto, and utilizes the geographic location of thecalling party mobile device to authorize the call in the event that thecalling party mobile device is within the limited geographical area ofthe called party rate plan (or reject the call in the event that thecalling party mobile device is outside the limited geographical area ofthe called party rate plan). Moreover, the pertinent called party rateplan corresponding to the request is used for accounting purposes forbilling the call. In alternative embodiment, the call profile datacommunicated to the call-setup-function of the MNO network in the calledparty provisioning loop of block 217 can include the mobile phone numberof the called party mobile device for use in authorizing the call andbilling. The MNO network can be adapted to hide the mobile phone numberof calling party mobile device as part of the information communicatedto the called party mobile device during call setup as well as on thebilling statements of the called party. The call-setup-function (30A or30B) of the MNO network returns a response (e.g., SIP response) to theservice softswitch 28 that carries an indication of connectionauthorization (or rejection), connection parameters (when authorized)and possibly other information, such as rate information for the call.

In block 219, logic 24 evaluates the call connection status provided bythe calling agent of softswitch 28 as a result of blocks 215 and 217 todetermine whether a connection has been established to both the callingparty user device and the called party user device. If so, theoperations continue to blocks 221 to 227. Otherwise, the operationbranches to blocks 229 to 233.

In block 221, softswitch 28 is controlled to bridge the connections tothe calling party mobile device and the called party mobile device. Suchbridging provides an end-to-end connection where the bearer traffic foreach leg of the call flows through the softswitch 28. This configurationestablishes connections between users while keeping their phone numbersprivate. In this mode, the softswitch 28 can exercise full control overthe call and disconnect calls in progress if necessary.

In block 223, logic 24 initiates call logging for the call. In thepreferred embodiment, such call logging operations stores a call record(26D) for the call in the information repository 26 (FIG. 3 ). The callrecord (26D) can include the start time, elapsed time, social networkuser id and domain for the called party, social network user id anddomain for the calling party, the phone numbers (or static IP addresses)for the user mobile device that terminates each call leg, and the AK (orapplication ID) for the social network application that requested thecall. Other information can be included such as phone number charged forthe call, a sequence number identifying the record, additional digits onthe called number used to route or charge the call, the result of thecall (whether it was answered, busy etc), the route for each leg of thecall, and any fault condition encountered.

In optional block 225, logic 24 control messaging interface 22 to returna “call success” message to the requesting application (i.e., App Logic1).

In optional block 227, the requesting application (i.e., App Logic 1)receives the “call success” message and performs predetermined processesbased thereon. For example, it is contemplated that the application canupdate the user display to provide an indication of call success.

In optional block 229, the softswitch 28 is controlled to bridge theconnection from the calling party mobile device to the resources of thevoicemail system 41 in order to allow the calling party to leave avoicemail message for access by the called party. In some circumstances(for example, where the called party answers and the calling party doesnot answer), softswitch 28 can be controlled to bridge the connectionfrom the called party mobile device to the resources of the voicemailsystem 41 in order to allow the called party to leave a voicemailmessage for access by the calling party.

In optional block 231, logic 24 control messaging interface 22 to returna “call failure” message to the requesting application (i.e., App Logic1).

In optional block 233, the requesting application (i.e., App Logic 1)receives the “call failure” message and performs predetermined processesbased thereon. For example, it is contemplated that the application canupdate the user display to provide an indication of call failure.

In a second embodiment of the present invention, the social networkapplications (e.g., App Logic 18A, 20A, 18B, 20B) and the service 21cooperate to initiate and service a voice call between users as providedin the flow chart of FIGS. 2B1 through 2B3. The operations begin inblock 251, where a user (user A) operates user device 12A and invokes asocial network application (referred to as “App Logic 1” and labeled18A) via the Internet. In response thereto, the social networkapplication 18A connects to the online social network service I (14A)through framework 16A to authenticate the user A, e.g., a logon processfor the service, for example, using the user name (billyway) andpassword (XXXX) assigned to user A. The framework 16A also provides forauthorization that controls access by the social network application 18Ato user A profile data (if such authorization has not yet beenprovided).

In block 253, once user A is authenticated and the applicationauthorized, the social network application 18A and the framework 16Aprovide a mechanism (for example, a token) that allows the socialnetwork application 18A to access user A profile data via the framework16A.

In block 255, user A interacts with the social network application 18Ato customize a user profile for the application. This involves defininga screen alias and possibly an image (or avatar) for user A that iscommunicated to other users during execution of the application. Forexample, during gaming applications, the screen alias and image (oravatar) can be displayed to identify the user A to other users of thegame, and thus hide the social network user ID for user A from otherusers of the game.

Similar operations are carried out by another user (userB—tomjones@facebook.com) to invoke and execute the social networkapplication (referred to as “App Logic 1” and labeled 18A) via theInternet.

In block 257, during execution of the social network application 18A,the application 18A presents user A with a link (or widget or otheruser-interface element) that is adapted to initiate a voice call to userB upon user interaction with the element. User B can be identified touser A by a screen alias associated thereto as described above, and thushide the social network user ID for user B from user A. User A theninteracts with the element (for example, by clicking on the link) toinitiate a voice call to user B, and the application 18A is notified ofthe request (for example, by an HTTP request). User A is thus designatedthe calling party and user B is designated the called party throughout.It is contemplated that the application-drive initiation of voice callscan be part of many different application scenarios. For example, duringa game application, a user can encounter an avatar for one or more otheractive users. In this scenario, the game application can present a link(or widget or other user-interface element) that is adapted to initiatea voice call between the active users (i.e., between user A and user B).In other example, during a media sharing application, a user can sharemedia with one or more other active users. In this scenario, the mediasharing application can present a link (or widget or otheruser-interface element) that is adapted to initiate a voice call betweenthe active users (i.e., between user A and user B). In yet anotherexample, during a dating application, a user can view a profile of otherusers of the application. In this scenario, the dating application canpresent a link (or widget or other user-interface element) that isadapted to initiate a voice call between users (i.e., between user A anduser B).

In response to the request initiated in block 257, the application 18Agenerates a displays a document on the user device 12A of user B.Preferably, the document is based on a template supplied dynamicallyfrom the Service 21. The document presents to user B a dialog box thatprompts for a response from user B. In the preferred embodiment, thedialog box provides a notification message together with a prompt forthree possible responses as follows:

-   -   <Screen Alias for User A> (or <SN user name for User A>) wishes        to call you, please select from:    -   <response 1> OK to call you    -   <response 2> do not permit call    -   <response 3> connect to voicemail        Note that the calling party User A can be identified to the        called party user B by a screen alias associated to user A as        described above, and thus hide the social network user ID for        user A from user B.

In block 261, the application 18A checks whether the response selectedby user B is <response 2>—do not permit call and thus provides anindication that user B does not want to permit the call. If so, the callprocess continues to block 291 to communicate the call failure to therequesting user A. Otherwise, the operations continue to block 263.

In block 263, the application 18A generates and sends a message tomessaging interface 22 of the service 21 over a communication linktherebetween (block 207). In the preferred embodiment, the message iscarried over an IP packet-based communication network linking theapplication 18A and the calling service 21 including the Internet asshown. The message preferably conforms to the SOAP/XML protocol to allowfor efficient exchange of the information within the message.Alternatively, the message can conform to a predetermined RESTfularchitecture. This message includes the following:

-   -   user name (billyway) and social network domain (facebook.com)        for the calling party;    -   user name (tomjones) and social network domain (facebook.com)        for the calling party;    -   data specifying the request type (e.g., a voice call request for        user B selection of <response 1>—Ok to call, or a voicemail        request for user B selection of <response 3>—connect to        voicemail;    -   a domain key for the corresponding social network domain (e.g.,        DK for facebook.com); and    -   an application key for the requesting social network application        (18A).

In block 265, the messaging interface 22 of the service 21 receives themessage communicated from application 18A in block 207.

In block 267, the logic block 24 evaluates the request type data carriedin the received message to determine if the request is a voicemailrequest. If so, the operations continue to block 289. Otherwise, theoperations continue to block 269.

In block 269, the logic block 24 evaluates the request type data carriedin the received message to determine if the request is a voicecallrequest. If so, the operations continue to block 271. Otherwise, anunexpected error is encountered and the operations continue to block 293to communicate the error to the requesting user A (and possibly to userB).

In block 271, logic block 24 performs a lookup of the informationrepository 26. As shown in FIG. 3 , the information repository 26 storesinformation in electronic form, the information pertaining to socialnetwork users of the service 21, social network application developersand the social network applications that interface to the service 21,and one or more MNOs that provide resources for connecting calls to thesocial network users of the service 21. The information repository 26further stores electronic information pertaining to the calls carriedout by operation of the service 21. Access to information repository 26is controlled according to each of the three user types as describedabove (type 1—social network users of the service, type 2—developerusers associated with social network application developers that developand/or maintain social network applications that interface to theservice, and type 3—MNO users that are associated with MNOs that provideresources for connecting calls to social network users of the service).In the preferred embodiment, the information repository 26 is realizedby an SQL database system as described above. In block 271, the query ofthe information repository 26 retrieves the following:

-   -   mobile device phone number, mobile carrier ID, and possibly        other user information (for example, calling rules) for the        calling party (billyway@facebook.com); and    -   mobile device phone number, mobile carrier ID, and possibly        other user information (for example, calling rules or blacklist        parameters) for the called party (tomjones@facebook.com).

In block 273, logic block 24 determines whether the call should beblocked. For example, the calling rules or blacklist info of the calledparty as retrieved from the information repository 26 can dictate thatthe call should be blocked (or not). In yet another example, the callingrules of the calling party as retrieved from the information repository26 can dictate that the call should be blocked (or not). In the eventthat logic block 24 determines that the call should be blocked, theprocessing continues to block 291. Otherwise, the processing continuesto block 275.

Blocks 275 and 277 involve the control of the softswitch 28 that is partof the service 21. The softswitch 28 includes switching logic that iscontrolled by a calling agent. The switching logic includes resourcesthat provide for bridging of connections that carry the bearer trafficfor the legs of the call as described above.

In the exemplary embodiment, in block 275 the calling agent of thesoftswitch 28 cooperates with the call-setup-function (30A or 30B) ofthe MNO network for the calling party (preferably identified by the MNOID of the calling party as retrieved from the information repository 26)to set up a connection (i.e., communication session) that carries bearertraffic for the leg of the call to the mobile device (29A or 29B) of thecalling party. At the MNO side, the call-setup-function (30A or 30B) ofthe respective MNO network interfaces to a Radio Network Controller (RNC34A or 34B) to carry out signaling functions with the calling partymobile device. If the call is accepted on the calling party mobiledevice, the call-setup-function (30A or 30B) of the respective MNOnetwork interfaces to the corresponding gateway function (32A or 32B) toallocate resources to provide bearer traffic to and from the callingparty mobile device (via the Base Station (36A or 36B) and RNC (34A or34B) coupled to the calling party mobile device) over the connection tothe softswitch 28. Typically, the respective gateway function (32A and32B) provides media mapping and/or transcoding functions betweenpotentially dissimilar networks.

In this manner, the resources of the MNO network of the calling partyprovides for bi-directional exchange of bearer traffic between thecalling party mobile device and the softswitch 28. In 3G CDMAarchitectures, the gateway function (32A or 32B) of the MNO network iscarried out by the Media Gateway (MGW), and the gateway control function(30A, 30B) is carried out by the MSC Server. In IMS architectures, thegateway function (32A or 32B) of the MNO network is carried out by theIMS Media Gateway (IMS-MGW), and the gateway control function (30A, 30B)is carried out by call session control functions (e.g., I-CSCF, S-CSCFand P-SCSF) in conjunction with the Media Gateway Control Function(MGCF). IN LTE-SAE architectures, the RNC and gateway functions (34A/32Aor 34B/32B) of the MNO network is carried out by the Gateway (GW), andthe gateway control function (30A, 30B) is carried out by the mobilitymanagement entity (MME). Similar functional elements are used in otherarchitectures.

In block 277, the calling agent of the softswitch 28 cooperates with thecall-setup-function (30A or 30B) of the MNO network for the called party(preferably identified by the MNO ID of the called party as retrievedfrom the information repository database 26) to set up a connection(i.e., communication session) that carries bearer traffic for the leg ofthe call to the mobile device (29A or 29B) of the called party. At theMNO side, the call-setup-function (30A or 30B) of the respective MNOnetwork interfaces to a RNC (34A or 34B) to carry out signalingfunctions with the called party mobile device. If the call is acceptedon the called party mobile device, the call-setup-function (30A or 30B)of the respective MNO network interfaces to the corresponding gatewayfunction (32A or 32B) to allocate resources to provide bearer traffic toand from the called party mobile device (via the Base Station (36A or36B) and RNC (34A or 34B) coupled to the calling party mobile device)over the connection to the softswitch 28. Typically, the respectivegateway function (32A and 32B) provides media mapping and/or transcodingfunctions between potentially dissimilar networks. In this manner, theresources of the MNO network for the called party provides forbi-directional exchange of bearer traffic between the called partymobile device and the softswitch 28.

The provisioning loops of blocks 275 and 277 are similar to steps 215and 217 described above with respect to FIGS. 4A and 4B.

In block 279, logic 24 evaluates the call connection status provided bythe calling agent of softswitch 28 as a result of blocks 275 and 277 todetermine whether a connection has been established to both the callingparty user device and the called party user device. If so, theoperations continue to blocks 281 to 287. Otherwise, the operationbranches to blocks 289 to 293.

In block 281, softswitch 28 is controlled to bridge the connections tothe calling party mobile device and the called party mobile device. Suchbridging provides an end-to-end connection where the bearer traffic foreach leg of the call flows through the softswitch 28. This configurationestablishes connections between users while keeping their phone numbersprivate. In this mode, the softswitch 28 can exercise full control overthe call and disconnect calls in progress if necessary.

In block 283, logic 24 initiates call logging for the call. In thepreferred embodiment, such call logging operations stores a call record(26D) for the call in the information repository 26 (FIG. 3 ). The callrecord (26D) can include the start time, elapsed time, social networkuser id and domain (and alias name, if any) for the called party, socialnetwork user id and domain (and alias name, if any) for the callingparty, the phone numbers for the user mobile device that terminates eachcall leg, and the AK (or application ID) for the social networkapplication that requested the call. Other information can be includedsuch as phone number charged for the call, a sequence number identifyingthe record, additional digits on the called number used to route orcharge the call, the result of the call (whether it was answered, busyetc), the route for each leg of the call, and any fault conditionencountered.

In optional block 285, logic 24 control messaging interface 22 to returna “call success” message to the requesting application (i.e., App Logic1).

In optional block 287, the requesting application (i.e., App Logic 1)receives the “call success” message and performs predetermined processesbased thereon. For example, it is contemplated that the application canupdate the user display for User A and User B to provide an indicationof call success.

In optional block 289, softswitch 28 is controlled to bridge theconnection from the calling party mobile device to the resources of thevoicemail system 41 in order to allow the calling party to leave avoicemail message for access by the called party. In some circumstances(for example, where the called party answers and the calling party doesnot answer), softswitch 28 can be controlled to bridge the connectionfrom the called party mobile device to the resources of the voicemailsystem 41 in order to allow the called party to leave a voicemailmessage for access by the calling party.

In optional block 291, logic 24 control messaging interface 22 to returna “call failure” message to the requesting application (i.e., App Logic1).

In optional block 293, the requesting application (i.e., App Logic 1)receives the “call failure” message and performs predetermined processesbased thereon. For example, it is contemplated that the application canupdate the user display to provide an indication of call failure.

Referring back to FIG. 3 , the electronic information stored in theinformation repository 26 preferably includes the following for aparticular social network user as illustrated in column 26A:

-   -   social network user ID (e.g., billyway);    -   social network domain (e.g., facebook.com) for the social        network user ID;    -   phone number for the mobile device of the social network user;        in the preferred embodiment, this phone number is an MSISDN        stored in non-volatile memory (e.g., SIM card) of the mobile        device of the social network user.    -   an MNO ID for the MNO that issued the user mobile device; this        MNO maintains an account with an associated rate plan for calls        to and/from the user mobile device;    -   global activation parameter for the mobile device of the social        network user; such global activation parameter can toggle        between an ON and OFF state; in the ON state, calls cannot be        placed to the user's mobile device; in the OFF state, all calls        to the user's mobile device are blocked;    -   global usage parameters, such as calling rules, blacklists or        whitelists specified by the social network user;    -   parameters pertaining to social network applications registered        by the user, including for each social network application        -   an app ID for the application,        -   a user alias name for the application (if any), and        -   application-specific usage parameters, such as calling            rules, blacklists or whitelists specified by the social            network user for the application;    -   a view (e.g., stored query) of call record information (26D) for        the social network user        -   for each call originated by the social network user, the            viewed call record information can include a start time,            elapsed time, MNO ID for the user (calling party), called            party alias name for the requesting application (or social            network user id and domain of the called party), and app ID            for requesting application;        -   for each calls received by the social network user, the            viewed call record information can include a start time,            elapsed time, MNO ID for the user (called party), calling            party alias name for the requesting application user (or            social network user id and domain of the calling party), and            app ID for requesting application;        -   the viewed call record information can also include summary            information derived therefrom (such as total number of calls            and/or total call minutes for calls initiated and/or            received by the social network user over a time period).            Other useful social network user information can be            maintained by the database 26 if desired. In the preferred            embodiment, the phone numbers for the user devices stored as            part of the database 26 follow the standard E.164 format,            SIP identifiers or other suitable URLs.

As illustrated in column 26B of FIG. 3 , the application developerinformation stored in the information repository 26 preferably includesthe following for each social network application developed by aparticular application developer:

-   -   the application key (AK) for the social network application;    -   an app ID for the social network application;    -   one or more social network domain(s) connected to by the social        network application (e.g., facebook.com);    -   a domain key (DK) for each social network domain(s) connected to        by the social network application; and    -   a view (i.e., stored query) to call record information (26D) for        calls requested by the social network application (i.e., start        time, elapsed time, user IDs (and/or alias names) and social        network domain for the parties of the call, and the app ID for        requesting application); it can also include summary information        derived therefrom (such as total number of calls and/or total        call minutes for calls initiated by an application over a time        period).        Other useful application developer information can be maintained        by the information repository 26 if desired.

As illustrated in column 26C of FIG. 3 , the MNO information stored inthe information repository 26 preferably includes the following for eachMNO that provides resources for connecting calls to users of the service21:

-   -   gateway information (for provisioning connections to the MNO);        and    -   a view (i.e., stored query) to call record information for calls        for serviced by the MNO (i.e., start time, elapsed time, phone        number for the user mobile device that is terminated by the MNO        for the call, and the app ID for requesting application).        Other useful MNO information can be maintained by the        information repository 26 if desired.

As illustrated in row 26D of FIG. 3 , the call record information storedin the information repository 26 preferably includes the following foreach call serviced by the Service 21: a start time, elapsed time, socialnetwork user id and domain (and alias name if any) for the called party,social network user id and domain (and alias name, if any) for thecalling party, the phone numbers for the user mobile device thatterminates each call leg, and the AK (or application ID) for the socialnetwork application that requested the call. Other information can beincluded such as phone number charged for the call, a sequence numberidentifying the record, additional digits on the called number used toroute or charge the call, the result of the call (whether it wasanswered, busy etc), the route for each leg of the call, and any faultcondition encountered.

Users register with the service 21 and interact with the service 21 tospecify the mobile phone number and carrier for the user's mobiledevice. Such information is stored and verified by a messaging loopbetween the specified device and the service 21. Once verified, theinformation for the user's mobile device is stored in the social networkuser record (26A) of the information repository database 26 (FIG. 3 ).

In the exemplary embodiment shown in FIGS. 5A and 5B, the userregistration process is invoked upon the user initiating a voice callthrough a social network application as set forth in FIG. 2 . Inresponse to the service receiving a request from the social networkapplication (step 209), the operations begin in block 501 where Logic 24queries the information repository 26 to determine if the Calling Party(User A) is registered with the service 21 for any social networkapplication (e.g., is there a social network user record for the callingparty that provides a registered mobile device for the given user). Ifso, the operations continue to block 503 to append the social networkuser record (26A) for the calling party in the information repository 26to include information specific to the requesting application. Suchinformation can include the AK (or application ID) for the requestingapplication if not already associated with the particular user record.Otherwise, the operations continue to blocks 505 and 507.

In block 505, the service 21 initiates interaction with the callingparty (i.e. User A), preferably via the requesting application (e.g.18A), whereby the calling party (User A) specifies the mobile number andthe MNO of a mobile device to be used for calls to the calling party(User A).

In block 507, logic 24 queries the information repository 26 todetermine if the mobile number specified by the calling party (User A)in block 505 is already registered by another user of the service. Ifnot, the operations continue to blocks 509 to 515. Otherwise, theoperations continue to blocks 523 to 529.

In block 509, logic 24 generates an authentication code (for example, arandom multi-digit alphanumeric code) for purposes of verifying themobile device number specified by the calling party (User A) in block505.

In block 511, the service 21 interacts with the calling party (User A)to present the authentication code generated in block 509. It can alsoutilize other communication channels (such an email message or socialnetwork message to the calling party) in order to present theauthentication code to the calling party (User A). The communicationfrom the service 21 to the calling party also preferably provides an SMSshort code assigned to the service 21 for the verification process.

In block 513, the calling party (User A) utilizes the mobile devicespecified in block 505 to send the authentication code as part of an SMSmessage addressed to the short code assigned to the service 21 asprovided in block 511.

In block 515, the service 21 receives the SMS message supplied from thecalling party mobile device (513) and addressed to its short code, andcompares the authentication code supplied therein to the authenticationcode communicated to the calling party in block 511. If theauthentication codes match, the operations continue to blocks 517 to519. Otherwise, the operations continue to block 521.

In block 517, logic 24 appends the social network user record (26A) forthe calling party (User A) in the information repository 26 to includeinformation specific to the calling party mobile device as well asinformation specific to the requesting application. Such informationincludes the mobile phone number and MNO ID for the calling party mobiledevice as well as the AK (or application ID) for the requestingapplication.

In block 519, the messaging verification loop of the registrationprocess has succeeded and the service 12 interacts with the callingparty (User A) to communicate such success. The service 21 can alsoutilize other communication channels (such an email message or socialnetwork message to the calling party) in order communicate such successto the calling party (User A).

Blocks 523 to 529 address the scenario where the mobile number specifiedby the calling party (User A) in block 505 is already registered byanother user of the service 21.

In block 523, logic 24 generates an authentication code (for example, arandom multi-digit alphanumeric code) for purposes of verifying themobile device phone number specified by the calling party (User A) inblock 505.

In block 525, the service 21 interacts with the calling party (User A)via the requesting application 18A to present the authentication codegenerated in block 523. The service 21 can also utilize othercommunication channels (such an email message or social network messageto the calling party) in order to present the authentication code to thecalling party (User A). The communication from the service 12 to thecalling party (user A) also preferably provides an SMS short codeassigned to the service 21 for the verification process.

In block 527, the calling party (User A) utilizes the mobile devicespecified in block 505 to send the authentication code as part of an SMSmessage addressed to the short code of the calling service as providedin block 525.

In block 529, the calling service 21 receives the SMS message suppliedfrom the calling party mobile device (527) and addressed to its shortcode, and compares the authentication code supplied therein to theauthentication code communicated to the calling party in block 525. Ifthe authentication codes match, the operations continue to block 531.Otherwise, the operations continue to block 521.

In 531, logic 24 deletes the mobile phone number from the other matchingsocial network user record (26A). Such operations automatically reclaimphone numbers that have been ported, lost, re-used or otherwisere-assigned to a new individual or organization. In this manner, theservice 21 provides a self-healing mechanism for the social network userrecords (26A) of the information repository 26 and thus insure accuracyof such user records. The operations then continue to block 517 wherelogic 24 appends the social network user record (26A) for the callingparty (User A) in the information repository 26 to include informationspecific to the calling party mobile device as well as informationspecific to the requesting application as described above and thenreport registration success to the calling party (user A) in block 519.

Block 521 addresses the scenario where the messaging verification loopof the registration process fails. In block 521, the service 21interacts with the calling party (User A) to communicate such failure.It can also utilize other communication channels (such an email messageor social network message to the calling party) in order communicatesuch failure to the calling party (User A).

The user registration process of FIGS. 5A and 5B is also be invoked forthe called party. In this manner, the called party interacts with thecalling service 21 to specify the mobile phone number and MNO for theuser's mobile device. Such information is stored and verified by amessaging loop between the specified device and the calling service 21.Once verified, the information for the social network user's mobiledevice is stored in the social network user record (26A) of theinformation repository 26 (FIG. 3 ). In the preferred embodiment, theuser registration process for all legs of the call are carried out inparallel.

It is also contemplated that user can register their phone numbers withthe service 21 by other means. For example, the registration process canbe carried out by an Interactive Voice Response system accessible bycalling a designated number, or by a web portal reachable over theInternet at designated URL. Each of these processes preferably employs achallenge process that involves the communication of an authenticationcode to the user and the user supplying the authentication code formatching and authentication as part of the registration process. In thepreferred embodiment, the device to which the registered phone number isto be assigned is used to communicate the authentication code forauthentication and authorization of the user as part of the registrationprocess. This human-challenge authentication loop preferably involvesboth the human that possess the particular device as well as thecommunication medium through which the particular device is registeredto ensure accuracy of the registration process.

Developers of social network applications register with the service 21to request issuance of application keys. Each application key providesauthentication of request messages that initiate voice calls from aparticular application. Once issued, the application key is stored in anapplication developer record (26B) of the ENUM database (FIG. 3 ).

In the exemplary embodiment shown in FIG. 6 , the developer registrationprocess begins in block 601 where the application developer requests anapplication key (AK) for a particular application and affiliate socialnetwork domain. This request can be communicated via email, a phonecall, or by submission of information as part of electronic forms servedto the respective developer over the Internet by an HTTP server or thelike as part of the access function 43.

In block 603, the service 21 verifies that the particular application ofthe request of block 601 is approved for the corresponding affiliatesocial domain network of the request of block 601. This can beaccomplished by a manual verification process. If not, the operationscontinue to block 605. Otherwise, the operations continue to blocks 607to 609.

In block 605, the service 21 reports a denial of the application key tothe developer. Such reporting can be communicated via email, a phonecall, or by submission of information as part of electronic forms servedto the respective developer over the Internet by an HTTP server and thelike as part of the access function 43.

In block 607, the service 21 issues an application key for theparticular application of the request of block 601 and updates theapplication developer record (26B) of the information repository 26 toinclude the application key (and possibly an application ID) for theparticular application.

In block 609, the service 21 reports the application key to thedeveloper. Such reporting can be communicated via email, a phone call,or by submission of information as part of electronic forms served tothe respective developer over the Internet by an HTTP server and thelike as part of the access function 43. The application developerutilizes the application key as part of the logic of the particularapplication that initiates the communication of request messages (step207) to the service 21. The request messages function to initiate voicecalls from the particular application. The application key authenticatessuch request messages as originating from the particular application.

The access function 43 of the service 21 provides a web portal thatallows social network users, application developer users and MNO usersto access information stored in the information repository 26. Theaccess function 43 controls access to the information stored in theinformation repository 26 as described above.

The access function 43 can authenticate users, application developersand carriers by any conventional authentication methods, such as usernames and passwords, biometrics, a passport or an ID-card or others.Multi-factor schemes can be employed utilizing more than one of thesemechanisms. Once authenticated, the access function provides forcontrolled access to designated information for the authenticated user.

The access function 43 preferably allows a type 1 social network user toreview and update user information (26A of FIG. 3 ) as well as generateand review user-specific reports. The user information can includeglobal activation parameters and/or application-specific activationparameters that selectively activate (or deactivate) the user'sregistered phone from being used in conjunction with the service 21. Theuser information can also include global and/or application specificusage parameters (e.g., whitelists/blacklists/alias). The user-specificreports can provide for details of calls placed by or to the respectivesocial network user as maintained by call record information viewable bythe social network user. It can also provide for filters (e.g., showcalls to a particular user, calls in a particular date range, callsplaced from a particular application) and summaries (e.g., call minutesfor a given time period). As described above in detail, the accessfunction 43 does not allow the social network user to access userinformation for other social network users as well as the applicationdeveloper information (26B of FIG. 3 ) and the MNO information (26C ofFIG. 3 ) of the information repository 26.

The access function 43 preferably allows type 2 application developerusers to review and update application developer information (26B ofFIG. 3 ) as well as generate and review developer-specific (orapplication-specific) reports. The developer-specific reports canprovide for details of calls place by one or more applications of therespective developer as maintained by the call record informationviewable by the corresponding application developer. It can also providefor filters (e.g., show calls placed from a particular application,calls in a particular date range, calls placed to/from a particularuser) and summaries (e.g., call minutes for a given time period). Asdescribed above in detail, the access function 43 disallows access toinformation from other application developers as well as social networkuser information (26A of FIG. 3 ) and MNO information (26C of FIG. 3 )of the information repository 26.

The access function 43 also preferably allows type 3 MNO users to reviewand update MNO information (26C of FIG. 3 ) as well as generate andreview MNO-specific reports. The MNO-specific reports can provide fordetails of calls serviced by the MNO as maintained by call recordinformation viewable by the MNO. It can also provide for filters (e.g.,show calls placed from a particular application, calls in a particulardate range, calls placed to/from a particular user) and summaries (e.g.,call minutes for a given time period). As described above in detail, theaccess function 43 disallows access to information from other MNOs aswell as social network user information (26A of FIG. 3 ) and applicationdeveloper information (26B of FIG. 3 ) of the information repository 26.

FIGS. 7A-7C is an exemplary message flow diagram illustrating theoperations carried out by the system of FIG. 1 in accordance with themethodology of the present invention. The message flow operates toprovision resources (and tears down such resources) that carry out avoice call between a calling party mobile device and a called partymobile device as initiated by the user interaction with a social networkapplication. It is assumed that a calling party user (user A) operatesuser device 12A and invokes a social network application (referred to as“App Logic 1” and labeled 18A) via the Internet. In response thereto,the social network application 18A connects to the online social networkservice I (14A) through framework 16A to authenticate the user A, e.g.,a logon process for the service, for example, using the user name(billyway) and password (XXXX) assigned to user A. The framework 16Aalso provides for authorization that controls access by the socialnetwork application 18A to user A profile data (if such authorizationhas not yet been provided). Once user A is authenticated and theapplication authorized, the social network application 18A and theframework 16A provide a mechanism (for example, a token) that allows thesocial network application 18A to access user A profile data via theframework 16A. Similar operations are carried out for social networkuser B.

In AA, during execution of the social network application 18A, theapplication 18A presents user A with a link (or widget or otheruser-interface element) that is adapted to initiate a voice call to userB (tomjones@facebook.com) upon user interaction with the element. User Athen interacts with the element (for example, by clicking on the link)to initiate a voice call to user B (block 205 or 257).

In AB, the application 18A generates and sends a message to messaginginterface 22 of the service 21 over a communication link therebetween(block 207 or 263).

In AC, the messaging interface 22 of the service 21 receives the messagecommunicated from application 18A and controls the logic block 24 toperform a lookup of the information repository 26 (block 211 or 271).

In block AD, the query of the information repository 26 retrieves thefollowing:

-   -   mobile device phone number, mobile carrier ID, and possibly        other user information (for example, calling rules) for the        calling party (billyway@facebook.com); and    -   mobile device phone number, mobile carrier ID, and possibly        other user information (for example, calling rules or blacklist        parameters) for the called party (tomjones@facebook.com).

In block AE, the logic block 24 determines whether the call should beblocked. For example, the calling rules or blacklist info of the calledparty as retrieved from the information repository 26 can dictate thatthe call should be blocked (or not). In yet another example, the callingrules of the calling party as retrieved from the information repository26 can dictate that the call should be blocked (or not). In the eventthat logic block 24 determines that the call should not be blocked, thelogic block 24 controls the calling agent of the softswitch 28 toperforms a provisioning loop (AF-AK) that carries out call set-up andsignaling with the gateway control function 30A of the MNO network forthe mobile device 29A of the calling party user A as well as aprovisioning loop (AM-AR) that carries out call set-up and signalingwith the gateway control function 30B of the MNO network for the mobiledevice (29B) of the called party B.

The provisioning loop AF-AK sets up connections (i.e., communicationsessions) that carry bearer traffic for the leg of the call to themobile device 29A of the calling party.

In AF, a provisioning request message (e.g., SIP request) iscommunicated from the softswitch 28 to the call-setup-function 30A ofthe MNO network that services the mobile device phone number of thecalling party mobile device. The provisioning request message includesthe mobile device phone number of the calling party mobile device andpossibly call profile data. The call profile data can provideinformation related to the call that can be used for authorizationand/or accounting purposes by the respective MNO. Thecall-setup-function 30A of the MNO network utilizes the mobile devicephone number and the call profile data to selectively authorize thecall. The call profile data can be used for accounting purposes by theMNO as needed.

Once the call is authorized, the call-setup-function 30A of the MNOnetwork performs mobile network call setup signaling in conjunction withsession progress and context activation with the softswitch 28 in AGthrough AK as is well known.

The connections that carry bearer traffic for the leg of the call to themobile device 29A of the calling party are represented graphically inAL.

The provisioning loop AM-AR sets up connections (i.e., communicationsessions) that carries bearer traffic for the leg of the call to themobile device 29B of the called party. Such connections are representedgraphically in AS.

In AM, a provisioning request message (e.g., SIP request) iscommunicated from the softswitch 28 to the call-setup-function 30B ofthe MNO network that services the mobile device phone number of thecalled party mobile device. The provisioning request message includesthe mobile device phone number of the called party mobile device andpossibly call profile data. The call profile data can provideinformation related to the call that can be used for authorizationand/or accounting purposes by the respective MNO. Thecall-setup-function 30B of the MNO network utilizes the mobile devicephone number and the call profile data to selectively authorize thecall. The call profile data can be used for accounting purposes by theMNO as needed.

Once the call is authorized, the call-setup-function 30B of the MNOnetwork performs mobile network call setup signaling in conjunction withsession progress and context activation with the softswitch 28 in ANthrough AR as is well known.

The connections that carry bearer traffic for the leg of the call to themobile device 29B of the called party are represented graphically in AS.

In AT, when the connections for both legs of the calls have beenestablished, the softswitch 28 is controlled to bridge the connectionsto the calling party mobile device and the called party mobile. Suchbridging provides an end-to-end connection where the bearer traffic foreach leg of the call flows through the softswitch 28. This configurationestablishes connections between users while keeping their phone numbersprivate. In this mode, the softswitch 28 can exercise full control overthe call and disconnect calls in progress if necessary.

In AU and AV, the logic 24 initiates call logging for the call. In thepreferred embodiment, such call logging operations stores a call record(26D) for the call in the information repository 26 (FIG. 3 ).

In AW and AX, the logic 24 control messaging interface 22 to return a“call success” message for presentation to the calling party on device12A.

In AZ, the called party terminates the call by signaling, which tearsdown the connections for the call and bridging function performed by thesoftswitch 28 in BA through BD. to the requesting application (i.e., AppLogic 1).

In BE and BD, the logic 24 updates the call records for the call in theinformation repository 26 (FIG. 3 ), for example to store the callduration and possibly other parameters.

In BE and BH, the logic 24 control messaging interface 22 to return a“call termination” message for presentation to the calling party ondevice 12A.

In alternate embodiment, the operations of the system components asdescribed herein can be modified to perform other operations thatprovision resources (and tears down such resources) that carry out avoice call between a calling party mobile device and a called partymobile device as initiated by the user interaction with a social networkapplication.

For example, during execution of the social network application, therequest can be communicated from the user machine to the service 21 byredirection and/or scripts.

In another example, the functionality of the softswitch 28 can bedistributed in nature as shown in FIG. 8 . In this configuration,multiple softswitches (for example, 4 shown as 28A, 28B, 28C, and 28D)are provided. Each softswitch (28A, 28B, 28C, or 28D) has one or moreinterconnection trunks 40′ to external gateways/switches (e.g., gatewayfunctions 32A and 32B of FIG. 1 ). In addition, each softswitch (28A,28B, 28C, or 28D) has one or more interconnection trunks 39′ to theother softswitches of the group 28′. The interconnection trunks 39′ and40′ can use time-division multiplexing (TDM), internet protocol (IP)and/or asynchronous transfer protocol (ATM) for communication of bearertraffic therebetween. Control logic 24 is interconnected to thesoftswitches (28A, 28B, 28C, and 28D) of the group 28′ by acommunication network 38′. The control logic 24 controls thesoftswitches (28A, 28B, 28C, and 28D) of the group 28′ to service thelegs of a particular voice calls. Bridging of the legs can beaccomplished within a given softswitch or by multiple softswitchesconnected over the interconnection trunks 39′.

The softswitches (28A, 28B, 28C, and 28D) of the group 28′ can begeographically distributed such that the softswitches (28A, 28B, 28C,and 28D) serves geographic areas which are remote from one another andpossibly remote from the physical location of the control logic 24.Among other things, handling a voice call by the distributedsoftswitches can be desirable in some situations, such as when thegeographic distribution of the softswitches allows the service operatorto minimize long distance fees that can be avoided by serving the callutilizing the distributed softswitches of the group 28′.

In yet another example, it is contemplated that the connections andbridging functionality for the voice call can be provisioned by theservicing operator gateway for the calling party and/or the calledparty. Caller ID blocking functionality can be invoked to maintain theprivate nature of the phone numbers to the parties of the call.

In still another example, the service as described herein can beintegrated into the services/application layer of an MNO network itselfin order to provide advanced services to the mobile users serviced bythe MNO. In this example, Caller ID blocking functionality of the MNOcan be invoked to maintain the private nature of the phone numbers tothe parties of the call.

Moreover, the operations of telecommunication service as describedherein can be extended to other advanced communication functions betweenonline social network users. For example, the softswitch of the servicecan be adapted to service voice calls to landlines over the PSTN and/orto SIP phones over the Internet, multiparty voice conferencing betweenusers, real-time chat between users, H.323 video conferencing betweenusers, file sharing between users, and media content streaming betweenusers. The service can also provide other communication functionsbetween users, such as SMS messaging, MMS messaging, email messaging,etc.

For SMS messaging, the input of the originating party generates a textstring that is supplied as part of the request message communicated tothe service 21. The request message also includes the user name anddomain of the recipient as well as the user name and domain of theoriginating party. The service 21 performs a lookup of the socialnetwork user information (26A) for the recipient user to retrieve thephone number for the mobile device of the recipient user, encapsulatesthe text string supplied in the request as part of an SMS messageaddressed to the mobile device of the recipient user, and forwards theSMS message to the MNO network of the recipient user.

For Callme functionality, a registered user of the service (referred toherein as the requesting subscriber) is presented with a Callme widgetassociated with another registered user of the service 21 (referred toherein as the recipient subscriber) during execution of the socialnetwork application. By clicking on this Callme widget, the socialnetwork application triggers the communication of a request message tothe service 21. Alternatively, the request message is triggered afterpresentation of a notification message and response submission from thecalled party (similar to block 259). The request message includes theuser name and domain of the requesting subscriber as well as the username and domain of the recipient subscriber. The service 21 performs alookup of the social network user information (26A) for the requestingsubscriber to retrieve the phone number (or static IP address) for thetelephony device of the requesting subscriber as well as a lookup of thesocial network user information (26A) for the recipient subscriber toretrieve the phone number (or static IP address) for the telephonydevice of the recipient subscriber. These numbers are then used to setup a telephony call between the telephony devices for the requesting andrecipient subscribers as described herein.

Such Callme functionality can also be extended to allow an unregistereduser of the service 21 to place a call to a registered user (referred toherein as the requesting user) of the service 21 during execution of thesocial network application. In this case, the unregistered user ispresented with a Callme widget associated with the registered user(referred to herein as the recipient subscriber) during execution of thesocial network application. By clicking on this Callme widget, thesocial network application triggers the communication of a requestmessage to the service 21. This request message includes the user nameand domain of the requesting user as well as the user name and domain ofthe recipient subscriber. The service 21 performs a lookup of the socialnetwork user information (26A) for the requesting user. This lookupfails because the requesting user is not registered with the service 21.The requesting user can then be presented with an interface thatprovides for registration with the service 21. After registration iscomplete (i.e., the requesting user has registered and verified anassociation to a mobile device identifier), the operations continue toset up a telephony call between the telephony devices for the requestingand recipient subscribers as described herein. Alternatively, in thecase where the lookup fails, the requesting user can be presented withan interface that allows the requesting user to enter a character stringthat represents a phone number for a device to call. This characterstring is supplied as part of a message to the service 21 and thesupplied phone number is used to set up a telephony call between thetelephony devices for the requesting user and recipient subscriber asdescribed herein.

Other telecommunication functions can be provided. For example, theservice 21 can be adapted to connect to a plurality of registereddevices for a given user. Such connections can be carried out inparallel or in an ordered sequence. The registered devices, and controlover the sequence of connections can be dictated by user informationupdated by the user through the access logic 43.

Advantageously, the service 21 as described herein carries out therequested telecommunication function while maintaining the privacy ofthe device identifiers (phone numbers) with respect to the parties aswell as to the social network application that was used to initiate thefunction. By maintaining such privacy, the device identifiers (phonenumbers) are hidden from (i.e., not presented to) the parties as well asto the social network application that was used to initiate thefunction. This affords greater protection against unwanted distributionof the private phone numbers of the parties.

It is also contemplated that static IP addresses can be used as deviceidentifiers for the social network user's telecommunication devices ofthe present invention. Such static IP addresses can be assigned to theuser devices by the network operator. Such as a static IP address ispreferably stored in a non-volatile memory of the respective device. Thestatic IP address is preferably permanent in nature. The static IPaddress can be stored in a pluggable memory card (e.g., SIM card) andloaded into the respective device if desired.

There have been described and illustrated herein several embodiments ofa system and method for establishing communication between online socialnetwork users. While particular embodiments of the invention have beendescribed, it is not intended that the invention be limited thereto, asit is intended that the invention be as broad in scope as the art willallow and that the specification be read likewise. Thus, whileparticular communication technologies, system architectures, messageformats and database architectures have been disclosed, it will beappreciated that other current and future communication technologies,system architectures, message formats and database architectures can beused as well to carry out the communication processing of the presentinvention as described herein. For example, it is contemplated that anonline social network itself can interface to the calling service toprovide advanced telecommunication functions carried out by the serviceas described herein. In this scenario, the online social network can beviewed as an application developer in registering and interface to theservice. In another example, it is contemplated that the unitarydatabase 26 as described herein and/or the access function associatedtherewith can be partitioned into multiple parts in order to segregatethe data for the intended access control. In another example, thesoftswitch can function in a routed mode such that all signalingmessages for the call flow through the softswitch. However, the bearertraffic does not flow through the softswitch but is exchangedgateway-to-gateway. In routed mode, the softswitch exercises substantialdegree of call control and can disconnect calls in progress ifnecessary. It therefore will be appreciated by those skilled in the artthat yet other modifications could be made to the provided inventionwithout deviating from its spirit and scope as claimed.

1.-85. (canceled)
 86. A method for supporting real-timetelecommunication, the method comprising: providing an informationrepository that stores a device identifier for a first social networkuser having a plan with an MNO (Mobile Network Operator), wherein thedevice identifier for the first social network user is stored in theinformation repository in response to a registration process thatauthenticates the first social network user and specifies the deviceidentifier for the first social network user; in response to receivingat least one message for initiating real-time telecommunication wherebythe first social network user is an initiator of the real-timetelecommunication, querying the information repository and retrievingfrom the information repository the device identifier for the firstsocial network user; and generating at least one message forcommunication to at least one gateway of the MNO, wherein the at leastone message includes the device identifier for the first social networkuser retrieved from the information repository, wherein the deviceidentifier for the first social network user is used by the least onegateway of the MNO in carrying out the real-time telecommunication. 87.A method according to claim 86, wherein: the at least one messagecommunicated to the at least one gateway of the MNO includes additionalinformation about the first social network user, wherein the additionalinformation is also used by the least one gateway of the MNO in carryingout the real-time telecommunication.
 88. A method according to claim 87,wherein: the additional information includes location information forthe first social network user, and the additional information is used bythe MNO in billing the real-time communication.
 89. A method accordingto claim 86, wherein: the at least one message for initiating real-timetelecommunication is communicated from a user device of the first socialnetwork user and generated by execution of a social network applicationon the user device of the first social network user; and the additionalinformation includes information that identifies the social networkapplication whose execution generated the at least one message.
 90. Amethod according to claim 86, wherein: the information repositoryfurther stores user data corresponding to the first social network userthat is queried in response to the least one message and used toselectively authorize the real-time telecommunication, wherein the userdata is selected from the group consisting of calling rules data,application-specific data, whitelist data and blacklist data associatedwith the first social network user.
 91. A method according to claim 86,wherein: the information stored in the information repository furthercomprises a social network username associated with the first socialnetwork user; the at least one message for initiating real-timetelecommunication includes the social network username for the firstsocial network user; and the querying uses the social network usernamefor the first social network user included in the at least one messageto query the information repository.
 92. A method according to claim 86,wherein: the at least one message for initiating real-timetelecommunication is communicated from a mobile communication device ofthe first social network user.
 93. A method according to claim 86,wherein: the device identifier for the first social network userincludes information that identifies a communication device for thefirst social network user; and/or the device identifier for the firstsocial network user comprises a number or address that identifies acommunication device for the first social network user.
 94. A methodaccording to claim 86, wherein: the real-time telecommunication isselected from the group consisting of a voice call, a multiparty voiceconference, a video conference, file sharing between users, and mediastreaming between users.
 95. A method according to claim 86, wherein:the device identifier for the first social network user retrieved fromthe information repository is used by the at least one MNO gateway toring or announce the real-time telecommunication on the devicecorresponding to the device identifier.
 96. A method according to claim86, wherein: the device identifier for the first social network userretrieved from the information repository is used by the at least oneMNO gateway to provision a connection or communication session thatcarries traffic for the real-time telecommunication.
 97. A methodaccording to claim 86, wherein: the registration process is configuredto verify possession of the device identified by the device identifierby communication to the device identified by the device identifier. 98.A method according to claim 97, wherein: the registration processinvolves at least one of: i) an SMS message sent to the deviceidentified by the device identifier; ii) communication from the deviceidentified by the device identifier; iii) an SMS message sent from thedevice identified by the device identifier to an assigned short code;iv) communication of an authentication code to a user via an interactivevoice response system and communication of the authentication code fromthe device identified by the device identifier; and v) an email messageor social network message to the first social network user.
 99. A methodaccording to claim 86, wherein: the information repository furtherstores a device identifier for a second social network user that is anintended recipient of the real-time telecommunication, wherein thedevice identifier for the second social network user is stored in theinformation repository in response to an additional registration processthat authenticates the second social network user and specifies thedevice identifier for the second social network user. in response toreceiving the at least one message for initiating real-timetelecommunication, the information repository is queried to retrievefrom the information repository the device identifier for the secondsocial network user; and at least one message is generated forcommunication to at least one gateway of the MNO, wherein the at leastone message includes the device identifier for the second social networkuser retrieved from the information repository, wherein the deviceidentifier for the second social network user is used by the least onegateway of the MNO in carrying out the real-time telecommunication. 100.A method according to claim 99, wherein: the device identifier for thesecond social network user includes information that identifies acommunication device for the second social network user; and/or thedevice identifier for the second social network user comprises a numberor address that identifies a communication device for the second socialnetwork user.
 101. A method according to claim 100, wherein: thecommunication device of the second social network user comprises amobile communication device.
 102. A method according to claim 99,wherein: the additional registration process is configured to verifypossession of the device identified by the device identifier for thesecond social network user by communication to the device identified bythe device identifier for the second social network user.
 103. A methodaccording to claim 102, wherein: the additional registration processinvolves at least one of: i) an SMS message sent to the deviceidentified by the device identifier for the second social network user;ii) communication from the device identified by the device identifierfor the second social network user; iii) an SMS message sent from thedevice identified by the device identifier for the second social networkuser to an assigned short code; iv) communication of an authenticationcode to a user via an interactive voice response system andcommunication of the authentication code from the device identified bythe device identifier for the second social network user; and v) anemail message or social network message to the second social networkuser.